3 Getting Started

Step 1

Prepare Yourself

(a)

Learn about the 1-System upgrade approach.

Upgrading 12c Release 1 (12.1.0.1) [with Bundle Patch 1], 12c Release 2 (12.1.0.2) to 12c Release 3 (12.1.0.3)

(b)

Review the important facts you need to know before you begin.

Chapter 2

Step 2

Upgrade Oracle Management Service and Oracle Management Repository

(a)

Meet the following prerequisites:

• Meet the Oracle Management Service-related prerequisites described in the chapter on installing Enterprise Manager Cloud Control, in the Oracle Enterprise Manager Cloud Control Basic Installation Guide.

• Upgrade to 12c Release 3 (12.1.0.3) is an out-of-place upgrade, therefore make sure your host meets the hardware requirements specific to 12c Release 3 (12.1.0.3) as described in Oracle Enterprise Manager Cloud Control Basic Installation Guide. Here, host refers to the host on which your current Enterprise Manager, which you want to upgrade, is running.

• Ensure that you are upgrading only on the supported platforms as listed in Supported Platforms for Upgrade.

• Ensure that the ports used by Enterprise Manager are not set to a value lower than or equal to 1024. If they are, then the upgrade will fail. Ports up to 1024 are typically reserved for root users (super users). Therefore, make sure the ports are greater than 1024.

• If you have BI Publisher installed on Enterprise Manager Cloud Control 12c installation that you are upgrading from, then stop the BI Publisher Managed Server named BIP using the WebLogic Administration Console. For instructions, refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

• Back up the OMS (the middleware home and the inventory), the Management Repository, and the Software Library. In case the upgrade fails, you can always restore using the backup.

  For instructions to back up, refer to Oracle Enterprise Manager Cloud Control Administrator's Guide.

• To understand the known issues and other important facts related to upgrade, see My Oracle Support note 1568143.1.

(b)

Check for any outstanding database service instance creation requests. If there are any requests in progress, allow them to complete. For requests that are scheduled, suspend them.

To do so, follow these steps.

1. In Cloud Control, from the Enterprise menu, select Infrastructure Cloud, then select Self Service Portal.

2. On the Infrastructure Cloud Self Service Portal page, right under the page title, select My Databases to view only database requests.

3. In the Requests table, for requests that are in progress, allow them to complete. For requests that are scheduled, suspend them.

   To suspend the scheduled requests, click the request name. Click the Deployment tab. Click the deployment procedure listed there, and suspend it.

(c)

Ensure that the tables in the Management Repository do not have any snapshots created.

To verify this, log in to the Management Repository and run the following SQL query as SYSMAN user:

select master , log_table from all_mview_logs where log_owner='<EM_REPOS_USER>

For example,

select master , log_table from all_mview_logs where log_owner='SYSMAN'

If there are snapshots created in a table, then the query displays the master table and the snapshot details. For example,

SQL> master log_table

em-violations em$violation_log

If there are snapshots, then drop them by running the following command as SYSMAN user:

SQL> Drop snapshot log on <master>

For example,

SQL> Drop snapshot log on em-violations

(d)

(CRITICAL MANDATORY STEP)

If you have the Management Repository configured in Oracle Database 11g Release 1 (11.1.0.7) or 11g Release 2 (11.2.0.1), then make sure you apply the following patches on the database. You can access My Oracle Support and search for these patches. If you find them for your respective database release and platform, download and apply them. For instructions, see the ReadMe file associated with the patch. If you do not apply these patches, you will run into upgrade failures that cannot be corrected.

For Oracle Database 11 Release 1 (11.1.0.7)

• On Unix platforms, apply patch 8405205.

• On Microsoft Windows (32 bit) platforms, apply patch 9082702 or patch 16345861 (Microsoft Windows bundle# 52), which includes patch 8405205 for Microsoft Windows 32-bit.

• On Microsoft Windows (64 bit) platforms, apply patch 9082709 or patch 16345862. Note that patch 16345862 is a superset patch that includes patch 9082709, so you can apply any one of them.

For Oracle Database 11g Release 2 (11.2.0.1)

• On Unix platforms, apply PSU 9352237 (11.2.0.1.1 Patch Set Update for Oracle Database).

  If you are on Linux platform, you have an option of applying patch 8405205 instead of PSU 9352237. If you have already applied patch 8405205 on the Linux platform, then you need not apply PSU 9352237. The PSU contains patch 8405205. Note that patch 8405205, as a standalone patch, is available only for Linux platform, and not for other Unix platforms.

• On Microsoft Windows (32 bit) platforms, apply patch 9595784

• On Microsoft Windows (64 bit) platforms, apply patch 9595786

For Oracle Database 11g Release 2 (11.2.0.2), 11g Release 2 (11.2.0.3), and 10g Release 2 (10.2.0.5)

Apply the generic patch 11061801.

Note: For some reason, if you do not apply these patches, and if the upgrade fails, then see My Oracle Support note 1568107.1 to verify the error in the log file, and to resolve the issue and proceed further.

(e)

Copy the emkey from the existing OMS to the existing Management Repository. To do so, run the following command on the old OMS home you are trying to upgrade:

$<OMS_HOME>/bin/emctl config emkey -copy_to_repos [-sysman_pwd <sysman_pwd>]

To verify whether the emkey is copied, run the following command:

<OMS_HOME>/bin/emctl status emkey

If the emkey is copied, then you will see the following message:

The EMKey  is configured properly, but is not secure.
Secure the EMKey by running "emctl config emkey -remove_from_repos".

(f)

Stop the OMS you are about to upgrade and also the other OMS instances that connect to it.

• If you are upgrading in graphical mode, then you can stop the OMS later as described in the note for Step (12) of Upgrading OMS and Management Repository in Graphical Mode.

• If you are installing software only and upgrading later in graphical mode, then you can stop the OMS later as described in the note for Step (4) in Configuring and Upgrading.

• If you are upgrading in silent mode, then stop the OMS now:

  $<OMS_HOME>/bin/emctl stop oms -all

(g)

Shut down the Management Agent that monitors the Management Services and Repository target, to prevent the Management Agent from connecting to the Management Repository for metric collections. Not shutting down this Management Agent might cause the OMS upgrade to fail.

(h)

Upgrade the OMS and the Management Repository. You can choose to upgrade in graphical or silent mode. You can also choose to install the software binaries at one point and upgrade them later in graphical or silent mode.

If you see an error message stating that you have not copied the emkey, then follow these steps:

1. Copy the emkey from the old OMS to the old Management Repository. To do so, run the following command from the old OMS home you are trying to upgrade:

   $<OMS_HOME>/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc <conndesc> -repos_user <username> [-repos_pwd <pwd>] -emkey_file <OMS_HOME>/sysman/config/emkey.ora

   For example,

   /u01/software/oracle/middleware/oms/bin/emctl config emkey -copy_to_repos_from_file -repos_conndesc (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost.mydomain.com)(PORT=1521)))(CONNECT_DATA=(SID=emrepos12))) -repos_user sysman -emkey_file /u01/software/oracle/middleware/oms/sysman/config/emkey.ora

   Note: Here, the Management Repository details are the details of the existing Management Repository you are trying to upgrade. And <OMS_HOME> is the OMS home you are trying to upgrade.

2. Try upgrading the OMS and the Management Repository again.

IMPORTANT: Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. To upgrade this Management Agent, use the Agent Upgrade Console.

For single-OMS environment, see Upgrading OMS and Management Repository in Graphical Mode, Upgrading OMS and Management Repository in Silent Mode, Installing Software Now and Upgrading Later in Graphical Mode, or Installing Software Now and Upgrading Later in Silent Mode

For multi-OMS environment (with additional OMS instances), see Upgrading Multi-OMS Environment

(i)

If you had BI Publisher installed on Enterprise Manager Cloud Control 12c installation that you are upgrading from, then it is necessary to install and upgrade to version 11.1.1.6.0 of BI Publisher. This install and upgrade are required for BI Publisher to be available in the new installation of Enterprise Manager 12c Release 3 (12.1.0.3). This upgrade is described in detail in the Oracle Enterprise Manager Advanced Installation and Configuration Guide. In particular, pass the -upgrade flag to the configureBIP command at the appropriate time, as specified in the guide. For instructions, refer to Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Step 3

Upgrade Oracle Management Agent

(a)

Review the important facts you need to know before you begin upgrading the Management Agents.

Before You Begin

(b)

Meet the prerequisites.

Prerequisites

(c)

Ensure that you restart the Management Agent that you shut down in Step (2g).

(d)

Upgrade the Management Agents.

IMPORTANT: Upgrade the Management Agent that was installed with the old OMS (that is, central agent) immediately after upgrading the old OMS. To upgrade this Management Agent, use the Agent Upgrade Console.

Upgrade Procedure

Step 4

Perform Postupgrade Task

(a)

Perform postupgrade tasks.

Performing General Postupgrade Steps

(b)

Reconfigure Oracle WebLogic Server with custom certificates

Reconfiguring Oracle WebLogic Server with Custom Certificates

(c)

Track the status of deferred data migration jobs.

Tracking the Status of Deferred Data Migration Jobs

(d)

Delete unwanted central agents

Deleting Unwanted Central Agents After Upgrading from 12.1.0.1 with Bundle Patch 1/12.1.0.2 to 12.1.0.3

(e)

Upgrade Application Dependency and Performance (ADP) engines and JVM Diagnostics (JVMD) engines

Chapter 6

(f)

Delete old OMS home

(Optional) Deleting the Old OMS Home

Step 1

Removing Standby Enterprise Manager

(a)

Remove all additional standby OMS instances.

"Removing Additional Standby OMS Instances" section of the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

(b)

Remove the first standby OMS.

"Removing the First Standby OMS" section of the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.

Step 2

Upgrade Primary Enterprise Manager

Upgrade the primary Enterprise Manager site, both OMS and Management Agents.

Upgrading Primary Enterprise Manager

Step 3

Redeploy Standby Enterprise Manager

Re-create the standby OMS environment using either a Standby WebLogic Domain or storage replication.

IMPORTANT: If you use a Standby WebLogic Domain, then ensure that you re-create with a domain name that is different from the one used for the primary site and for the old standby site.

"Enterprise Manager Disaster Recovery" chapter of the Oracle Enterprise Manager Cloud Control Administrator's Guide for details.